Servicing packets in a virtual network and a software-defined network (SDN)

ABSTRACT

In one embodiment, an apparatus includes a processor and logic configured to designate one of a plurality of endpoint virtual network identifiers (EPVNIDs) for each endpoint device in a network, wherein each EPVNID is configured to be shared by one or more endpoint devices, designate a common waypoint virtual network identifier (WPVNID) for all transparent waypoint devices in the network which perform a same function, designate a unique WPVNID for each routed waypoint device in the network, designate a common virtual network identifier (VNID) for all virtual switches in a single virtual network, wherein a different VNID is designated for each virtual network, and create a service chain table comprising each VNID, WPVNID, and EPVNID designated in the network individually correlated with at least a pair of VNIDs: a source VNID and a destination VNID, based on one or more policies affecting application of services to packets in the network.

BACKGROUND

The present invention relates to service appliances in virtual networks,and more particularly, this invention relates to service chaining invirtual networks and software-defined networks (SDNs).

Network virtualization is implemented by many vendors using overlaytechnologies, such as Virtual Extensible Local Area Network (VXLAN),Network Virtualization using Generic Routing Encapsulation (NVGRE),etc., to form tunnels, where an identifier is used to indicate a virtualnetwork for each tunneled packet. These technologies enable multiplevirtual networks to be utilized over the same physical network. Usually,a virtual switch component in a host or a virtualization layer (e.g., ahypervisor) provides the virtual ports which may be used to associatevirtual machines (VMs) to the various virtual networks.

Even though communication within a virtual network is a given, it ispossible to allow or control communication across virtual networks. Inphysical networks, it is possible to use service appliances, such asthose which implement firewalls, transcoding, load balancing, etc.Normally, the service appliances are inserted as a “bump in the wire”between the networks and/or services. These kind of service appliances(e.g., “waypoints”) are not currently supported in virtual networks.However, since network virtualization abstracts physical Layer-2/Layer-3networks, the use of physical appliances in a virtual network becomes aserious challenge. A bump in the wire insertion of one or more serviceappliances is not possible in virtual networks, as multiple virtualnetworks may share the same physical infrastructure and serviceappliances may not be able to distinguish between packets belonging toone specific virtual network from all the others.

There are some mechanisms available to allow for the insertion ofservice appliances in overlay networks defined by a SDN. Once theservice appliances are inserted into the overlay network, the managementand control plane configure the data forwarding layers so that dataframes in the overlay network follow the path defined by the overlaynetwork administrator, e.g., the SDN controller. However, there iscurrently no solution which allows for a service appliance to beinserted into an overlay network without requiring the service applianceto engage in some control plane activity with other components. Thiscontrol plane activity is a potential drawback, and should be avoidedwhen possible.

SUMMARY

In one embodiment, an apparatus includes a processor and logicintegrated with the processor, executable by the processor, orintegrated with and executable by the processor, the logic beingconfigured to designate one of a plurality of endpoint virtual networkidentifiers (EPVNIDs) for each endpoint device in a network, whereineach EPVNID is configured to be shared by one or more endpoint devices,designate a common waypoint virtual network identifier (WPVNID) for alltransparent waypoint devices in the network which perform a samefunction, designate a unique WPVNID for each routed waypoint device inthe network, designate a common virtual network identifier (VNID) forall virtual switches in a single virtual network, wherein a differentVNID is designated for each virtual network, and create a service chaintable comprising each VNID, WPVNID, and EPVNID designated in the networkindividually correlated with at least a pair of VNIDs: a source VNID anda destination VNID, based on one or more policies affecting applicationof services to packets in the network.

In another embodiment, a method includes designating one of a pluralityof EPVNIDs for each endpoint device in a network, wherein each EPVNID isconfigured to be shared by one or more endpoint devices, designating acommon WPVNID for all transparent waypoint devices in the network whichperform a same function, designating a unique WPVNID for each routedwaypoint device in the network, designating a common VNID for allvirtual switches in a single virtual network, wherein a different VNIDis designated for each virtual network, and creating a service chaintable comprising each VNID, WPVNID, and EPVNID designated in the networkindividually correlated with at least a pair of VNIDs: a source VNID anda destination VNID, based on one or more policies affecting applicationof services to packets in the network.

In yet another embodiment, a computer program product for servicingpackets includes a computer readable storage medium having programinstructions embodied therewith, where the computer readable storagemedium is not a transitory signal per se, and where the programinstructions are executable by a processor to cause the processor toperform a method including designating, by the processor, one of aplurality of endpoint virtual network identifiers (EPVNIDs) for eachendpoint device in a network, wherein each EPVNID is configured to beshared by one or more endpoint devices; designating, by the processor, acommon waypoint virtual network identifier (WPVNID) for all transparentwaypoint devices in the network which perform a same function;designating, by the processor, a unique WPVNID for each routed waypointdevice in the network; designating, by the processor, a common virtualnetwork identifier (VNID) for all virtual switches in a single virtualnetwork, wherein a different VNID is designated for each virtualnetwork; and creating, by the processor, a service chain tablecomprising each VNID, WPVNID, and EPVNID designated in the networkindividually correlated with at least a pair of VNIDs: a source VNID anda destination VNID, based on one or more policies affecting applicationof services to packets in the network.

Other aspects and embodiments of the present invention will becomeapparent from the following detailed description, which, when taken inconjunction with the drawings, illustrate by way of example theprinciples of the invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

FIG. 1 illustrates a network architecture, in accordance with oneembodiment.

FIG. 2 shows a representative hardware environment that may beassociated with the servers and/or clients of FIG. 1, in accordance withone embodiment.

FIG. 3 is a simplified diagram of a virtualized data center, accordingto one embodiment.

FIG. 4 is a simplified diagram of a system in accordance with oneembodiment.

FIG. 5A is a block diagram of a distributed virtual switch system inaccordance with one embodiment.

FIG. 5B is a block diagram of a distributed virtual switch system inwhich services are applied to packets in accordance with an exemplaryembodiment.

FIG. 6 is a diagram of a packet format according to one embodiment.

FIG. 7 is a block diagram of a service chain in accordance with oneembodiment.

FIG. 8 is a block diagram of a service chain in accordance with anotherembodiment.

FIG. 9 is a flowchart of a method, according to one embodiment.

FIG. 10 is a flowchart of a method, according to one embodiment.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating thegeneral principles of the present invention and is not meant to limitthe inventive concepts claimed herein. Further, particular featuresdescribed herein can be used in combination with other describedfeatures in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and theappended claims, the singular forms “a,” “an” and “the” include pluralreferents unless otherwise specified. It will be further understood thatthe terms “comprises” and/or “comprising,” when used in thisspecification, specify the presence of stated features, integers, steps,operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

In one approach, once a service appliance configuration is pushed to thecontrol plane, a virtual switch queries the control plane regardingwhere to direct a particular overlay data frame (overlay-encapsulatedpacket) to, when the virtual switch does not already have thedestination from a previous query. The control plane, which has fullknowledge of the topology and the configuration of the overlay network,returns the next hop for the frame (which could be a service appliance).At each point/hop of the data frame's path to the final destination,this decision is taken with the help of the control plane. Some of thecontrol plane messages and computations which are used to perform thesetasks are disclosed herein according to various embodiments. Since therecould be a variety of overlay flows in a deployment, the control planeentity is configured to optimize search algorithms to return the nexthop of a data frame quickly. A variety of tables may be used to achievethe desired speed for a query from a virtual switch.

Also, network virtualization technology currently does not supportinsertion of virtual service appliances into virtual networks bycatering to specific packet forwarding requirements of the virtualservice appliance. In one embodiment, virtual service appliances (e.g.,“waypoints”) are supported by providing special ports on each of thevirtual switches for connecting to the virtual service appliance(s).These special ports will cater to the packet forwarding needs of thewaypoints.

In one general embodiment, an apparatus includes a processor and logicintegrated with and/or executable by the processor, the logic beingconfigured to designate one of a plurality of endpoint virtual networkidentifiers (EPVNIDs) for each endpoint device in a network, whereineach EPVNID is configured to be shared by one or more endpoint devices,designate a common waypoint virtual network identifier (WPVNID) for alltransparent waypoint devices in the network which perform a samefunction, designate a unique WPVNID for each routed waypoint device inthe network, designate a common virtual network identifier (VNID) forall virtual switches in a single virtual network, wherein a differentVNID is designated for each virtual network, and create a service chaintable comprising each VNID, WPVNID, and EPVNID designated in the networkindividually correlated with at least a pair of VNIDs: a source VNID anda destination VNID, based on one or more policies affecting applicationof services to packets in the network.

In another general embodiment, a method includes designating one of aplurality of EPVNIDs for each endpoint device in a network, wherein eachEPVNID is configured to be shared by one or more endpoint devices,designating a common WPVNID for all transparent waypoint devices in thenetwork which perform a same function, designating a unique WPVNID foreach routed waypoint device in the network, designating a common VNIDfor all virtual switches in a single virtual network, wherein adifferent VNID is designated for each virtual network, and creating aservice chain table comprising each VNID, WPVNID, and EPVNID designatedin the network individually correlated with at least a pair of VNIDs: asource VNID and a destination VNID, based on one or more policiesaffecting application of services to packets in the network.

In yet another general embodiment, an apparatus includes a processor andlogic integrated with and/or executable by the processor, the logicbeing configured to receive one or more packets to be switched to a nexthop, the one or more packets indicating a destination address and afirst VNID, send a query to a controller in order to determine a servicechain for the one or more packets, the query including the first VNIDand the destination address, and receive a response that includes thenext hop and a next routed hop for the one or more packets.

FIG. 1 illustrates an architecture 100, in accordance with oneembodiment. As shown in FIG. 1, a plurality of remote networks 102 areprovided including a first remote network 104 and a second remotenetwork 106. A gateway 101 may be coupled between the remote networks102 and a proximate network 108. In the context of the presentarchitecture 100, the networks 104, 106 may each take any formincluding, but not limited to a LAN, a WAN such as the Internet, publicswitched telephone network (PSTN), internal telephone network, etc.

In use, the gateway 101 serves as an entrance point from the remotenetworks 102 to the proximate network 108. As such, the gateway 101 mayfunction as a router, which is capable of directing a given packet ofdata that arrives at the gateway 101, and a switch, which furnishes theactual path in and out of the gateway 101 for a given packet.

Further included is at least one data server 114 coupled to theproximate network 108, and which is accessible from the remote networks102 via the gateway 101. It should be noted that the data server(s) 114may include any type of computing device/groupware. Coupled to each dataserver 114 is a plurality of user devices 116. Such user devices 116 mayinclude a desktop computer, lap-top computer, hand-held computer,printer or any other type of logic. It should be noted that a userdevice 111 may also be directly coupled to any of the networks, in oneembodiment.

A peripheral 120 or series of peripherals 120, e.g., facsimile machines,printers, networked and/or local storage units or systems, etc., may becoupled to one or more of the networks 104, 106, 108. It should be notedthat databases and/or additional components may be utilized with, orintegrated into, any type of network element coupled to the networks104, 106, 108. In the context of the present description, a networkelement may refer to any component of a network.

According to some approaches, methods and systems described herein maybe implemented with and/or on virtual systems and/or systems whichemulate one or more other systems, such as a UNIX system which emulatesan IBM z/OS environment, a UNIX system which virtually hosts a MICROSOFTWINDOWS environment, a MICROSOFT WINDOWS system which emulates an IBMz/OS environment, etc. This virtualization and/or emulation may beenhanced through the use of VMWARE software, in some embodiments.

In more approaches, one or more networks 104, 106, 108, may represent acluster of systems commonly referred to as a “cloud.” In cloudcomputing, shared resources, such as processing power, peripherals,software, data, servers, etc., are provided to any system in the cloudin an on-demand relationship, thereby allowing access and distributionof services across many computing systems. Cloud computing typicallyinvolves an Internet connection between the systems operating in thecloud, but other techniques of connecting the systems may also be used.

FIG. 2 shows a representative hardware environment associated with auser device 116 and/or server 114 of FIG. 1, in accordance with oneembodiment. Such figure illustrates a typical hardware configuration ofa workstation having a central processing unit 210, such as amicroprocessor, and a number of other units interconnected via a systembus 212.

The workstation shown in FIG. 2 includes a Random Access Memory (RAM)214, Read Only Memory (ROM) 216, an I/O adapter 218 for connectingperipheral devices such as disk storage units 220 to the bus 212, a userinterface adapter 222 for connecting a keyboard 224, a mouse 226, aspeaker 228, a microphone 232, and/or other user interface devices suchas a touch screen and a digital camera (not shown) to the bus 212,communication adapter 234 for connecting the workstation to acommunication network 235 (e.g., a data processing network) and adisplay adapter 236 for connecting the bus 212 to a display device 238.

The workstation may have resident thereon an operating system such asthe Microsoft Windows® Operating System (OS), a MAC OS, a UNIX OS, etc.It will be appreciated that a preferred embodiment may also beimplemented on platforms and operating systems other than thosementioned. A preferred embodiment may be written using JAVA, XML, C,and/or C++ language, or other programming languages, along with anobject oriented programming methodology. Object oriented programming(OOP), which has become increasingly used to develop complexapplications, may be used.

Referring now to FIG. 3, a conceptual view of an overlay network 300 isshown according to one embodiment. In order to virtualize networkservices, other than simply providing a fabric path (connectivity)between devices, services may be rendered on packets as they movethrough the gateway 314 which provides routing and forwarding forpackets moving between the non-virtual network(s) 312 and the VirtualNetwork A 304 and Virtual Network B 306. The one or more virtualnetworks 304, 306 exist within a physical (real) network infrastructure302. The network infrastructure 302 may include any components,hardware, software, and/or functionality typically associated withand/or used in a network infrastructure, including, but not limited to,switches, connectors, wires, circuits, cables, servers, hosts, storagemedia, operating systems, applications, ports, I/O, etc., as would beknown by one of skill in the art. This network infrastructure 302supports at least one non-virtual network 312, which may be a legacynetwork.

Each virtual network 304, 306 may use any number of VMs 308, 310. In oneembodiment, Virtual Network A 304 includes one or more VMs 308, andVirtual Network B 306 includes one or more VMs 310. As shown in FIG. 3,the VMs 308, 310 are not shared by the virtual networks 304, 306, butinstead are exclusively included in only one virtual network 304, 306 atany given time.

Components of an overlay network 300 typically identify where to routepackets based on a virtual network identifier, referred to as a VNI orVNID. This is typically a 24-bit code or number, which excludes 0x0 and0xFFFFFF. The overlay network 300 has the capability of tunnelingLayer-2 (L2) packets over the Layer-3 (L3) network by encapsulating theL2 packets into an overlay header. This may be performed using virtualextensible local area network (VXLAN) or some other overlay capableprotocol, such as locator/ID separation protocol (LISP), overlaytransport virtualization (OTV), Network Virtualization using GenericRouting Encapsulation (NVGRE), etc.

The packet may also be encapsulated in a user datagram protocol (UDP)and internet protocol (IP) UDP/IP header. The overlay network 300 mayinclude one or more point-to-point tunnels, and/or point-to-multipointtunnels. In addition, any of these tunnels may be created, removed,altered and modified based on any number of factors, such as new devicesbeing added to the overlay network 300, removal of devices from theoverlay network 300, startup of any end devices, i.e., devices managingtunnel end points, such as virtual overlay network gateways,Hypervisors, switches capable of overlay functionality, etc.

In order for a device to manage a tunnel, there needs to be a mappingbetween an original packet's source address, destination address, and atunnel identifier. In this way, a physical server is capable offorwarding the encapsulated original packet to the proper destinationdevice.

A virtual network may be identified by a tunnel endpoint identifier,referred to as a Virtual Network ID (VNID). In one embodiment, there maybe multiple different types or categories of VNIDs. In one suchembodiment, an Endpoint VNID (EPVNID) may be used to denote sourceand/or destination devices, such as hosts, VMs, etc. There are norestrictions on the number of devices that may exist in any singleEPVNID, and of course, there may be many unique EPVNIDs that exist in aphysical network infrastructure. According to another embodiment, aWaypoint VNID (WPVNID) may be used to denote a single waypoint device(“bump in the wire,” such as a VM, appliance, etc.) that is positionedbetween other devices in a path through the physical infrastructure.Each waypoint device is assigned a unique WPVNID so that it may beuniquely described in a path definition through the network.

According to one embodiment, waypoint policies may be used to define theway that traffic should flow between a source device and a destinationdevice (source and destination endpoints). These policies may be createdfor each port on a distributed virtual switch, or just for some of theports as determined by the administrator. Each waypoint policy may beapplied based on any factor or combination of factors, such as on thebasis of a source destination media access control (MAC) address, adestination MAC address, a protocol, a Layer-4 (L4) port, aninter-virtual network, etc. Each policy may identify a unique WPVNID andmay be made available to all the virtual switches, such as via asoftware-defined network (SDN) controller or some other device that isin communication with all the virtual switches in the overlay networkand/or SDN.

Table 1 shows an exemplary port identifier (Port ID)-based waypointpolicy that may be implemented in a virtual network according to oneembodiment.

TABLE 1 Waypoint Port ID Waypoint Policy ID (WPVNID) 10 — — 20 SMAC =11:22:33:44:55:66 & TCP Port 488 100, 101 30 DMAC = aa:bb:cc:dd:ee:ff200, 220

In this exemplary Port ID-based waypoint policy, no action is specifiedfor Port ID 10, while on Port ID 20 for each packet or frame having asource MAC address (SMAC) of 11:22:33:44:55:66 and a transmissioncontrol protocol (TCP) Port identifier of 488, the packet or frame isrouted through a waypoint device having a WPVNID of 100 and waypointdevice having a WPVNID of 101, in that order. Also, for Port ID 30, eachpacket or frame having a destination MAC address (DMAC) ofaa:bb:cc:dd:ee:ff, the packet or frame is routed through a waypointdevice having a WPVNID of 200 and a waypoint device having a WPVNID of220, in that order.

Table 2 shows an exemplary intra virtual network-based waypoint policythat may be implemented in a virtual network according to oneembodiment.

TABLE 2 VNID Waypoint ID (WPVNID) 15 300 25 400, 401 100 500, 550, 551

As shown in Table 2, in this exemplary intra virtual network-basedwaypoint policy, for each packet or frame specifying VNID 15, the packetor frame is routed through a waypoint device having a WPVNID of 300.Also, for each packet or frame specifying VNID 25, the packet or frameis routed through a waypoint device having a WPVNID of 400 and awaypoint device having a WPVNID of 401, in that order. Furthermore, foreach packet or frame specifying VNID 100, the packet or frame is routedthrough a waypoint device having a WPVNID of 500, a waypoint devicehaving a WPVNID of 550, and a waypoint device having a WPVNID of 551, inthat order.

Table 3 shows an exemplary inter virtual network-based waypoint policythat may be implemented in a virtual network according to oneembodiment.

TABLE 3 S-VNID D-VNID Waypoint ID (WPVNID) 10 15 600 20 25 700, 701, 704

As shown in Table 3, in this exemplary inter virtual network-basedwaypoint policy, for each packet or frame specifying a source VNID(S-VNID) of 10 and a destination VNID (D-VNID) of 15, the packet orframe is routed through a waypoint device having a WPVNID of 600. Also,for each packet or frame specifying a S-VNID of 20 and a D-VNID of 25,the packet or frame is routed through a waypoint device having a WPVNIDof 700, a waypoint device having a WPVNID of 701, and a waypoint devicehaving a WPVNID of 704, in that order.

Of course, these are just examples of waypoint policies, and actualwaypoint policies may be based on any combination of factors,characteristics, and/or values stored within and without packets and/orframes received transmitted in a virtual network.

Now referring to FIG. 4, a system 400 is shown according to oneembodiment. The system 400 includes a host 402 in communication with awaypoint or policy manager 404. The waypoint or policy manager 404 maybe implemented in a SDN controller 424 or some other suitable controllerconfigured to communicate with the host(s) 402, or may be a standalonedevice, module, processor, etc. More than one host 402 may be present inthe system 400, according to various embodiments. The host 402 includesa virtual switch 406 (which may also include a virtual switch extension408), along with a virtual switch agent 410 configured to communicatewith the virtual switch 406 (and possibly the virtual switch extension408), in order to handle packet ingress and egress through the virtualswitch 406 (and possibly the virtual switch extension 408). The virtualswitch 406 is configured to handle normal packet (packets which do notindicate handling by any WPVNIDs) ingress and egress along with packetingress and egress from and to waypoint device(s) that are connected tothe host 402. Should a virtual switch extension 408 be included in thevirtual switch 406, it may be configured to handle packet ingress andegress from and to waypoint device(s) that are connected to the host402, while the normal packet ingress and egress is handled by thevirtual switch 406. Should no waypoint devices be connected to the host402, then the virtual switch extension 408 will not be utilized.

The virtual switch 406 may include a plurality of VM ports 416, each VMport 416 being capable of communicating with one VM 420 connected to thevirtual switch 406. Also, the virtual switch 406 and/or the virtualswitch extension 408 includes one or more waypoint ports 418, eachwaypoint port 418 configured to communicate with one waypoint device 422connected to the waypoint port 418.

In one embodiment, when the virtualization layer 412 is a Hypervisor,the virtual switch 406 may be implemented as a ‘vSwitch,’ the virtualswitch agent 410 may be implemented as a ‘vswitch agent,’ and/or thevirtual switch extension 408 may be implemented as a ‘vSwitchextension,’ terms which are specific to Hypervisor.

The host 402 also includes an application programming interface (API)agent 414 which is independent of the virtualization layer 412. The APIagent 414 is configured to interact and communicate with the policymanager 404, among other tasks and function known in the art.

Each VM port 416 on the virtual switch 406 is associated with a VNID,with VM ports 416 having the same VNID when they are within and/or onthe same virtual network. Each waypoint device 422 service is withinand/or on a unique VNID referred to as a WPVNID, with no other VM 420and/or waypoint device 422 providing a different service being withinand/or on that WPVNID. Put another way, there may be multiple waypointdevices 422 in a single VNID when each provides the exact samefunctionality. This may be implemented in high-availability waypointdevice functionality.

Now referring to FIG. 5A, a distributed virtual switch system 500 isshown to describe how policy information may be made available to eachvirtual switch on each of the hosts, e.g., first host 524, second host526, third host 528, etc. In order to share this policy information,each virtual switch is configured to create a tunnel between endpointdevices such that the traffic will pass-though desired waypointdevice(s) (when configured to do so according to the waypoint policy).

When a packet or frame ingresses from a VM port 520, a policy/rulelookup is applied. This policy/rule may dictate that the packet or frameis routed through none, one, or multiple waypoint devices or appliancesbefore being transmitted to its final destination endpoint device.

In one example, as shown in FIG. 5B, the policy/rule dictates that thepacket or frame is routed through waypoint devices 502, 504, 506, and508 before being transmitted to an endpoint device 510. Therefore, thepacket or frame is tunneled to the first waypoint device 502 accordingto the policy/rule, with a VNID in a header of the packet or frame beingset to the WPVNID of the target (first) waypoint device 502. The packetor frame is then mapped to an egress port 512 based on the WPVNIDspecified in the packet. The packet or frame is egressed via the port512 where the first waypoint device 502 is connected.

The packet or frame then is ingressed from the port 512 connected to thefirst waypoint device 502, and the policy/rule lookup is applied againto determine the next destination of the packet or frame. In thisexample, the next destination is the second waypoint device 504 in thesecond host 526. Therefore, the packet or frame is tunneled to thesecond waypoint device 504 according to the policy/rule, with a VNID inthe header of the packet or frame being set to the WPVNID of the target(second) waypoint device 504. The packet or frame is then mapped to anegress port 514 based on the WPVNID specified in the packet. The packetor frame is egressed via the port 514 where the second waypoint device504 is connected.

The packet or frame then is ingressed from the port 514 connected to thesecond waypoint device 504, and the policy/rule lookup is applied againto determine the next destination of the packet or frame. In thisexample, the next destination is the third waypoint device 506 in thethird host 528. Therefore, the packet or frame is tunneled to the thirdwaypoint device 506 according to the policy/rule, with a VNID in theheader of the packet or frame being set to the WPVNID of the target(third) waypoint device 506. The packet or frame is then mapped to anegress port 516 based on the WPVNID specified in the packet. The packetor frame is egressed via the port 516 where the third waypoint device506 is connected.

The packet or frame then is ingressed from the port 516 connected to thethird waypoint device 506, and the policy/rule lookup is applied againto determine the next destination of the packet or frame. In thisexample, the next destination is the fourth waypoint device 508 that isalso in the third host 528. Therefore, a VNID in the header of thepacket or frame is set to the WPVNID of the target (fourth) waypointdevice 508, the packet or frame is mapped to an egress port 518 based onthe WPVNID specified in the packet, and the packet or frame is egressedvia the port 518 where the fourth waypoint device 508 is connected.Then, after the packet or frame is ingressed from the port 518, a VNIDin the header of the packet or frame is set to the EPVNID of the targetendpoint device 510, the packet or frame is mapped to an egress port 522based on the EPVNID specified in the packet or frame, and the packet orframe is egressed via the port 522 where the endpoint device 510 isconnected.

Virtual service appliances in the network may be implemented in a numberof different ways. One such way is a transparent implementation via L2,which is referred to as a bump in the wire and/or bridged. This type ofvirtual service appliance implementation is transparent to other VMs,and does not change the MAC and/or IP address of the packet'sdestination. Some examples of transparent virtual service appliancesinclude a L2 firewall service appliance, an intrusion detection system(IDS), an intrusion protection system (IPS), etc.

A virtual service appliance may also be implemented as a routed-networkaddress translation (NAT) implementation, which is explicitly addressedby VMs using a front-end IP address, terminate incoming connections, andinitiate outgoing connections with a new source address. Some examplesof routed-NAT virtual service appliances include a L4-L7 applicationdelivery controller (ADC), a web proxy, etc.

Another virtual service appliance may be implemented as arouted-explicit gateway implementation, which is explicitly configuredas a subnet gateway by VMs, performs L3 routing (changes source MACaddress), and interfaces in each subnet that is being serviced. Someexamples of routed-explicit gateway virtual service appliances include aL3 firewall, NAT, a web proxy, etc.

According to another implementation, a virtual service appliance may beimplemented as a routed-implicit gateway implementation, which may be asubnet gateway for VMs, where cross-subnet traffic is transparentlydirected to the virtual service appliance, such that no per-VM subnetgateway configuration is required. Some examples of routed-implicitgateway virtual service appliances include a L3 firewall, NAT, a webproxy, etc.

According to one embodiment, a user may configure the waypoints in thevirtual network such that desired services may be rendered to packets orframes therein. These virtual service appliances may be attached to aspecific VNID and/or network. A WPVNID identifies the type of serviceprovided by that waypoint, while multiple (similar functionality)waypoints may co-exist on the same VNID. One configuration for twowaypoints providing the same service in a virtual network is where bothservice appliances are active, and traffic may be distributed (loadbalanced) between them. In another embodiment, the two waypointsproviding the same service in a virtual network may have anactive/standby relationship.

Now referring to FIG. 6, a packet format 600 is shown according to oneembodiment. This packet format 600 may be used in a VXLAN implementationto encapsulate original packet(s) in order to tunnel the originalpacket(s) across the virtual network to have services applied thereto bythe various virtual service appliances located in a virtual network. Ofcourse, other packet headers than that shown in FIG. 6 may be used forthis encapsulation which may adhere to other overlay technologies, suchas NVGRE, LISP, OTV, etc., which may include additional fields, lessfields, and/or different fields than those shown in the exemplary packetformat 600, as would be understood by one of skill in the art.

The packet format 600 includes an outer destination MAC address (DMAC)field 602, an outer source MAC address (SMAC) field 604, an outer VLANtag (such as a IEEE 802.1Q) field 606, an outer destination IP address(DIP) field 608, an outer source IP address (SIP) field 610, an outeruser datagram protocol (UDP) field 612, a VNID field 614 (which mayinclude a protocol specific ID, such as a VXLAN ID), an inner DMAC field616, an inner SMAC field 618, an optional inner VLAN tag field 620, anda payload 622 (which typically includes one or more original packets).

The VNID field 614 may be used to store a WPVNID indicating the waypointdevice (such as a virtual service appliance) to which the packet is tobe directed, an EPVNID indicating the endpoint device to which thepacket is to be directed to, and/or a standard VNID indicating thevirtual network of the packet. In one embodiment, the VNID field 614 maybe 24 bits in length, 12 bits in length, 32 bits in length, or someother suitable length as determined by an administrator and recognizedby all devices in the virtual network.

In one embodiment, the outer DIP field 608, the VNID field 614, and theinner DMAC field 616 may be populated by a virtual switch based oninformation retrieved from a SDN controller. The outer DIP field 608 isconfigured to store the next/final hop, which is typically a virtualswitch (such as an OpenFlow switch, DOVE switch, etc.). The inner DMACfield 616 is configured to store an intermediate or destination VM,appliance, or virtual appliance MAC address for the original packet inthe payload 622.

In another embodiment, a query may be sent to a SDN controller or someother suitable controller by the virtual switch (or DOVE switch,OpenFlow switch, etc.) to retrieve other information. For example, theinner SMAC field 618 is an optional field that is configured to store aninput to the SDN controller for flow path determination and/ormodification. Also, an inner SIP field and an inner DIP field of theoriginal packet in the payload 622 may also be configured to be inputsto the SDN controller for flow path determination and/or modification.The VNID associated with the originating VM or appliance may bedetermined by the query to the SDN controller or some other suitablecontroller by the virtual switch according to a further embodiment.

Therefore, according to one embodiment, there may be severalinteractions between the SDN controller and the one or more virtualand/or SDN-enabled switches in the virtual network. In another example,the one or more virtual and/or SDN-enabled switches may query the SDNcontroller for a location lookup, the query including a VNID along witha DIP and/or DMAC. The SDN controller may respond to this query with anext hop VNID, a next hop virtual or SDN-enabled switch, and/or a nexthop DMAC (from an inner packet header). Furthermore, the one or morevirtual and/or SDN-enabled switches may query the SDN controller for apolicy lookup, the query including a VNID along with a DIP and/or DMACand a SIP and/or SMAC. The SDN controller may respond to this query witha next hop VNID, a next hop virtual or SDN-enabled switch, and/or a nexthop DMAC (from an inner packet header).

In order for these queries to be effective, the SDN controller mayinclude and/or create the following mappings: VM to switch (given a VM,the virtual and/or SDN-enabled switch location is known), VM to hostVNID, <MAC, VNID> to VM, <IP, VNID> to VM, VNID to [list of VMs in theVNID]. With these mappings, any query for information may be respondedto with appropriate information allowing the packet to be transmitted toappropriate intermediate hops and the ultimate destination device.

In each virtual and/or SDN-enabled switch, these mappings may beincluded in a forwarding table, according to one embodiment. Thisforwarding table may be utilized to determine a destination address fora received packet which is to be forwarded on, and may be modified bythe SDN controller to ensure that it is up-to-date.

Furthermore, in another example, the SDN controller may cause thevirtual and/or SDN-enabled switches to flush the forwarding table storedtherein, with a query for this purpose including a source VNID alongwith a list of MAC addresses or a list of destination VNIDs. A responseto this query is an acknowledgement of completion of the flush. Flushingincludes deleting and/or removing all or some of the entries in theforwarding table.

With reference to FIG. 7, a service chain 700 is shown according to oneembodiment. In this service chain 700, a VM 702 (within EPVNID 10) on aclient host 704 sends a query to reach a database (DB) 716 on a server718 within EPVNID 11. The service chain, as devised the policy/ruleimplementation, includes a firewall 706 within WPVNID W1 (which acts asa transparent virtual service appliance), an IDS/IPS device 708 withinWPVNID W2 (which acts as a routed virtual service appliance), a router710 within VNID W3, a firewall 712 within WPVNID W4 (which acts as atransparent virtual service appliance), and a router 714 within VNID W5.Of course, any other virtual service appliances may be used in a servicechain, in addition to, in place of, and/or instead of one or more of thevirtual service appliances shown in the exemplary service chain 700 ofFIG. 7.

Table 4 below shows the results of the various queries which are madealong the service chain 700, in one example.

TABLE 4 Next Routed Querying VNID (Source, Destination) VNID Pairs HopHop 10 (10, 11), (10, W2) W1 W2 W1 (10, 11), (10, W2) W2 W2 W2 (10, 11),(10, W3) W3 W3 W3 (10, 11), (10, W5) W4 W5 W4 (10, 11), (10, W5) W5 W5W5 (10, 11) 11 11

The VNID may be derived from a <SIP, DIP> tuple in one embodiment.

Also, the querying VNID is the virtual and/or SDN-enabled switch makingthe policy lookup query, the (Source, Destination) VNID Pairs may bederived from the policy query, i.e., SIP, DIP, SMAC, DMAC, etc. The nexthop indicates the next service in the chain, and the routed hopindicates the DMAC to be put in the inner packet header. When the routedhop is a WVNID (indicating that the routed hop is a waypoint device),then one of the VM ports (it does not matter which one) registered onthat WVNID is returned as the inner DMAC address. When the routed hop isan EPVNID (indicating that the routed hop is an endpoint device), thenthe actual destination VM port is returned as the inner DMAC address.

FIG. 8 shows a service chain 800 with a load balancer 810 according toone embodiment. In this exemplary service chain 800, a client 802 and aserver 814 are endpoint devices having EPVNIDs 10 and 11, respectively.The service chain 800 includes a firewall 806 (transparent) withinWPVNID W1 and a firewall 812 (transparent) within WPVNID W4, an IPS/IDSdevice 808 (routed) within WPVNID W2, and the load balancer 810 withinWPVNID W3. Of course, any other virtual service appliances may be usedin a service chain, in addition to, in place of, and/or instead of oneor more of the virtual service appliances shown in the exemplary servicechain 800 of FIG. 8.

The load balancer 810 is configured to terminate connections coming infrom the client 802 and create new connections to the server 814 (suchas for access to the DB).

The service chain 800 is defined by an administrator, such as a user,the SDN controller, or some other entity capable of making such adetermination. In this example, the service chain 800 is {W1→W2→W3→W4}.The policy/rule which implements this service chain may also be definedby an administrator, such as a user, the SDN controller, or some otherentity capable of making such a determination. In this example, thepolicy is {10→11}={W1→W2→W3→W4}.

When the client 802 sends packets to an address in VNID W3, the SIP isset as VNID 10, and the DIP is set as VNID W3. However, when the VM(load balancer 810) in VNID W3 sends a packet to the server 814 in VNID11, there are two ways of handling the egress: keep the SIP of VNID 10and DIP of VNID 11, or set a new SIP of VNID W3 and DIP of VNID 11.

In order to resolve this ambiguity, one or more service chain tables maybe maintained in the SDN controller or some other entity suitable forproviding service chain information to the various components in thevirtual network. Table 5 shows one such table according to one exemplaryembodiment.

TABLE 5 Querying VNID (Source, Destination) VNID Pairs Next Hop RoutedHop 10 (10, W3) W1 W2 W1 (10, W3) W2 W2 W2 (10, W3) W3 W3 W3 (10, 11),(W3, 11) W4 W4 W4 (10, 11), (W3, 11) 11 11

In one embodiment, the transition from EPVNID 10 to WPVNID W3 may betreated as one (S*, D*) combination for implementation in the servicechain [W1,W2]. Furthermore, in another embodiment, the transition fromEPVNID 10 to EPVNID 11 may be treated as several (S*, D*) combinationsfor implementation in the service chain [W4].

This results in the service chain table to be adjusted as it appears inTable 6, below.

TABLE 6 Querying Next Routed VNID (Source, Destination) VNID Pairs HopHop 10 (10, W3), (10, W2) W1 W2 W1 (10, W3), (10, W2) W2 W2 W2 (10, W3)W3 W3 W3 (10, 11), (10, W4) + (W3, 11), (W3, W4) W4 W4 W4 (10, 11), (W3,11) 11 11

The service chain tables may be used in the following context. An inputand/or query is received from a SDN-enabled switch and/or a virtualswitch that includes a query VNID for the service appliance/VM and adestination address (a DIP and/or DMAC), along with an optional SIPand/or SMAC (for flow path determination purposes).

The SDN controller or some other suitable entity derives the source VNIDfrom the SIP (and/or SMAC), which may be accomplished via a lookup on ahash table which correlates such addresses to one another, such as via asingle operation O(1). Then, the destination VNID is derived from theDIP (and/or DMAC), which may also be accomplished via a lookup on thehash table which correlates such addresses to one another, such as via asingle operation O(1). Then the service chain table is consulted, suchas via a query with the query VNID and the source and destination VNIDin a tuple, e.g., Query VNID+(Source VNID, Destination VNID). Thisprovides a result, which includes a next hop and a next routed hop,e.g., Answer=Next Hop+Next Routed Hop. The next hop determines the nextvirtual and/or SDN-enabled switch+VNID, while the next routed hopdetermines the inner MAC address. This lookup costs a total of O(1).

Now referring to FIG. 9, a flowchart of a method 900 is shown accordingto one embodiment. The method 900 may be performed in accordance withthe present invention in any of the environments depicted in FIGS. 1-8,among others, in various embodiments. Of course, more or less operationsthan those specifically described in FIG. 9 may be included in method900, as would be understood by one of skill in the art upon reading thepresent descriptions.

Each of the steps of the method 900 may be performed by any suitablecomponent of the operating environment. For example, in variousembodiments, the method 900 may be partially or entirely performed by amainframe, a server, a storage controller, an operating system of astorage system, or some other device having one or more processors andlogic integrated with and/or executable by the processors. Theprocessor, e.g., processing circuit(s), chip(s), and/or module(s)implemented in hardware and/or software, and preferably having at leastone hardware component may be utilized in any device to perform one ormore steps of the method 900. Illustrative processors include, but arenot limited to, a central processing unit (CPU), an application specificintegrated circuit (ASIC), a field programmable gate array (FPGA), etc.,combinations thereof, or any other suitable computing device known inthe art.

As shown in FIG. 9, method 900 may initiate with operation 902, whereone of a plurality of EPVNIDs for each endpoint device in a network isdesignated. Each EPVNID is configured to be shared by one or moreendpoint devices, as determined by a network administrator.

In operation 904, a common WPVNID is designated for all transparentwaypoint devices in the network which perform the same function. Thisoperation has a caveat, multiple transparent waypoint devices whichperform the same function are not implemented on a single host, suchthat only one transparent waypoint device performing a single functionis implemented on any single host.

In operation 906, a unique WPVNID is designated for each routed waypointdevice in the network. In this way, each routed waypoint device may beuniquely addressed and receive traffic accordingly.

In operation 908, a common VNID is designated for all virtual switchesin a single virtual network. In this way, each virtual network will havea unique VNID from all other virtual networks so that a different VNIDis designated for each virtual network.

In operation 910, a service chain table is created that includes eachVNID, WPVNID, and EPVNID designated in the network individuallycorrelated with at least a pair of VNIDs: a source VNID and adestination VNID, based on one or more policies affecting application ofservices to packets in the network. These policies may be designated bythe administrator, user, or automatically by some other suitable entityknown in the art.

In another embodiment, the service chain table may also include a nexthop and a next routed hop individually correlated to each VNID, WPVNID,and EPVNID designated in the network.

The service chain table may be similar to one of those shown in Tables4-5, in various embodiments. Furthermore, the policies may berepresented by one of those shown in Tables 1-3, in various embodiments.

In one embodiment, the method 900 may further include receiving a queryto determine a service chain for one or more packets, the queryincluding a query VNID and a destination address. Furthermore, the queryVNID represents the VNID for the one or more packets. After receivingthis query, a next hop and a next routed hop may be determined for theone or more packets, according to one embodiment.

In a further embodiment, method 900 may also include deriving a firstdestination VNID using the destination address and deriving a firstsource VNID using a source address included in the query. This may beperformed according to any of the methods described herein, along withothers known in the art. In one embodiment, the next hop and the nextrouted hop may be determined by consulting the service chain table usingthe query VNID, the first destination VNID, and a first source VNID inorder to retrieve the next hop and the next routed hop.

According to another embodiment, method 900 may include sending the nexthop and the next routed hop in response to the query, such as to avirtual and/or SDN-enabled switch in the network (or some other devicewhich sent the query).

Now referring to FIG. 10, a flowchart of a method 1000 is shownaccording to one embodiment. The method 1000 may be performed inaccordance with the present invention in any of the environmentsdepicted in FIGS. 1-8, among others, in various embodiments. Of course,more or less operations than those specifically described in FIG. 10 maybe included in method 1000, as would be understood by one of skill inthe art upon reading the present descriptions.

Each of the steps of the method 1000 may be performed by any suitablecomponent of the operating environment. For example, in variousembodiments, the method 1000 may be partially or entirely performed by amainframe, a server, a storage controller, an operating system of astorage system, or some other device having one or more processors andlogic integrated with and/or executable by the processors. Theprocessor, e.g., processing circuit(s), chip(s), and/or module(s)implemented in hardware and/or software, and preferably having at leastone hardware component may be utilized in any device to perform one ormore steps of the method 1000. Illustrative processors include, but arenot limited to, a CPU, an ASIC, a FPGA, etc., combinations thereof, orany other suitable computing device known in the art.

As shown in FIG. 10, method 1000 may initiate with operation 1002, whereone or more packets are received to be switched to a next hop, the oneor more packets indicating a destination address and a first VNID. Thefirst VNID is associated with the one or more packets and indicate avirtual network to which the one or more packets belong.

In operation 1004, a query is sent to a controller in order to determinea service chain for the one or more packets, the query including thefirst VNID and the destination address. The controller may be a policymanager, a waypoint manager, a SDN controller (such as an OpenFowcontroller, DOVE controller, etc.), or some other controller of a typeknown in the art that is suitable for handling such requests.

In operation 1006, a response to the query is received that includes thenext hop and a next routed hop for the one or more packets. Thisresponse may be received from the same entity to which the query wassent or some other entity or intermediate entity in the network.

Method 1000 may further include encapsulating the one or more packets ina tunnel header, the tunnel header indicating a destination address asthe next hop. Also, a destination address of the one or more packets maybe designated as the next routed hop. Also, the method 1000 may includesending the one or more packets encapsulated in the tunnel header to thenext hop using a tunnel created therebetween in order to ensure that theone or more packets flow through each waypoint device designated in aflow from the controller.

In one embodiment, the controller may be a SDN controller and the methodmay be implemented on a device configured to communicate with the SDNcontroller via a common protocol, such as a virtual switch in a host, aSDN-enabled switch, a DOVE switch, etc.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Moreover, a system according to various embodiments may include aprocessor and logic integrated with and/or executable by the processor,the logic being configured to perform one or more of the process stepsrecited herein. By integrated with, what is meant is that the processorhas logic embedded therewith as hardware logic, such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), etc. By executable by the processor, what is meant is that thelogic is hardware logic; software logic such as firmware, part of anoperating system, part of an application program; etc., or somecombination of hardware and software logic that is accessible by theprocessor and configured to cause the processor to perform somefunctionality upon execution by the processor. Software logic may bestored on local and/or remote memory of any memory type, as known in theart. Any processor known in the art may be used, such as a softwareprocessor module and/or a hardware processor such as an ASIC, a FPGA, acentral processing unit (CPU), an integrated circuit (IC), a graphicsprocessing unit (GPU), etc.

It will be clear that the various features of the foregoing systemsand/or methodologies may be combined in any way, creating a plurality ofcombinations from the descriptions presented above.

It will be further appreciated that embodiments of the present inventionmay be provided in the form of a service deployed on behalf of acustomer to offer service on demand.

Some of the advantages of the systems and methods described hereininclude not needing to alter or further encapsulate packets in order totransport them via a virtual service appliance. Also, a serviceappliance is able to be added and/or inserted into an overlay networkwithout any changes needing to be made to the service appliance, as theservice appliance is not required to participate in control planeactivities other than declaring what category of appliance it is priorto deployment.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

What is claimed is:
 1. An apparatus comprising a processor and logicintegrated with the processor, executable by the processor, orintegrated with and executable by the processor, the logic beingconfigured to cause the processor to: designate one of a plurality ofendpoint virtual network identifiers (EPVNIDs) for each endpoint devicein a network, wherein each EPVNID is configured to be shared by one ormore endpoint devices; designate a common waypoint virtual networkidentifier (WPVNID) for all transparent waypoint devices in the networkwhich perform the same function; designate a unique WPVNID for eachrouted waypoint device in the network; designate a common virtualnetwork identifier (VNID) for all virtual switches in a single virtualnetwork, wherein a different VNID is designated for each virtualnetwork; and create a service chain table comprising each VNID, WPVNID,and EPVNID designated in the network individually correlated with atleast a source VNID and a destination VNID, based on one or morepolicies affecting application of services to packets in the network. 2.The apparatus as recited in claim 1, wherein multiple transparentwaypoint devices which perform the same function are not implemented ona single host.
 3. The apparatus as recited in claim 1, wherein the logicis further configured to: receive a query to determine a service chainfor one or more packets, the query including a query VNID and adestination address, the query VNID being for the one or more packets;and determine a next hop and a next routed hop for the one or morepackets.
 4. The apparatus as recited in claim 3, wherein the logic isfurther configured to: derive a first destination VNID using thedestination address; and derive a first source VNID using a sourceaddress included in the query.
 5. The apparatus as recited in claim 4,wherein the logic configured to determine the next hop and the nextrouted hop is further configured to consult the service chain tableusing the query VNID, the first destination VNID, and a first sourceVNID.
 6. The apparatus as recited in claim 3, wherein the logic isfurther configured to send the next hop and the next routed hop inresponse to the query.
 7. The apparatus as recited in claim 1, whereinthe service chain table further comprises a next hop and a next routedhop individually correlated to each VNID, WPVNID, and EPVNID designatedin the network.
 8. A method, comprising: designating one of a pluralityof endpoint virtual network identifiers (EPVNIDs) for each endpointdevice in a network, wherein each EPVNID is configured to be shared byone or more endpoint devices; designating a common waypoint virtualnetwork identifier (WPVNID) for all transparent waypoint devices in thenetwork which perform the same function; designating a unique WPVNID foreach routed waypoint device in the network; designating a common virtualnetwork identifier (VNID) for all virtual switches in a single virtualnetwork, wherein a different VNID is designated for each virtualnetwork; and creating a service chain table comprising each VNID,WPVNID, and EPVNID designated in the network individually correlatedwith at least a source VNID and a destination VNID, based on one or morepolicies affecting application of services to packets in the network. 9.The method as recited in claim 8, wherein multiple transparent waypointdevices which perform the same function are not implemented on a singlehost.
 10. The method as recited in claim 8, further comprising:receiving a query to determine a service chain for one or more packets,the query including a query VNID and a destination address, the queryVNID being for the one or more packets; and determining a next hop and anext routed hop for the one or more packets.
 11. The method as recitedin claim 10, further comprising: deriving a first destination VNID usingthe destination address; and deriving a first source VNID using a sourceaddress included in the query.
 12. The method as recited in claim 11,wherein the determining the next hop and the next routed hop comprisesconsulting the service chain table using the query VNID, the firstdestination VNID, and a first source VNID.
 13. The method as recited inclaim 10, further comprising, sending the next hop and the next routedhop in response to the query.
 14. The method as recited in claim 8,wherein the service chain table further comprises a next hop and a nextrouted hop individually correlated to each VNID, WPVNID, and EPVNIDdesignated in the network.
 15. A computer program product for servicingpackets, the computer program product comprising a computer readablestorage medium having program instructions embodied therewith, whereinthe computer readable storage medium is not a transitory signal per se,the program instructions executable by a processor to cause theprocessor to perform a method comprising: designating, by the processor,one of a plurality of endpoint virtual network identifiers (EPVNIDs) foreach endpoint device in a network, wherein each EPVNID is configured tobe shared by one or more endpoint devices; designating, by theprocessor, a common waypoint virtual network identifier (WPVNID) for alltransparent waypoint devices in the network which perform the samefunction; designating, by the processor, a unique WPVNID for each routedwaypoint device in the network; designating, by the processor, a commonvirtual network identifier (VNID) for all virtual switches in a singlevirtual network, wherein a different VNID is designated for each virtualnetwork; and creating, by the processor, a service chain tablecomprising each VNID, WPVNID, and EPVNID designated in the networkindividually correlated with at least a source VNID and a destinationVNID, based on one or more policies affecting application of services topackets in the network.
 16. The computer program product of claim 15,wherein multiple transparent waypoint devices which perform the samefunction are not implemented on a single host.
 17. The computer programproduct of claim 15, wherein the method further comprises: receiving, bythe processor, a query to determine a service chain for one or morepackets, the query including a query VNID and a destination address, thequery VNID being for the one or more packets; and determining, by theprocessor, a next hop and a next routed hop for the one or more packets.18. The computer program product of claim 17, wherein the method furthercomprises: deriving, by the processor, a first destination VNID usingthe destination address; and deriving, by the processor, a first sourceVNID using a source address included in the query.
 19. The computerprogram product of claim 18, wherein determining the next hop and thenext routed hop includes consulting the service chain table using thequery VNID, the first destination VNID, and a first source VNID.
 20. Thecomputer program product of claim 17, wherein the method furthercomprises sending, by the processor, the next hop and the next routedhop in response to the query.